Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "tpl-routes">
    <p>Provide a list of the public transport routes available for a given agency, line or passing by a specific stop.</p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>agency
            <span class="property-type">string</span>
        </dt>
        <dd>URI of the agency whose lines are to be retrieved</dd>
        <dt>line
            <span class="property-type">string</span>
        </dt>
        <dd>URI or shortName of a line (if URI is provided the agency is not needed)</dd>
        <dt>busstopname
            <span class="property-type">string</span>
        </dt>
        <dd>URI or name of a stop (if URI is provided the agency is not needed)</dd>
        <dt>geometry
            <span class="property-type">boolean</span>
        </dt>
        <dd> true/false, if true it returns a “hasGeometry” property for each service stating if the service has a complex WKT
            geometries (linestring, polygon) associated with it (if parameter is missing “false” is assumed)</dd>
    </dl>

    <h3>Outputs</h3>
    <dl class="message-properties">
        <dd> It provides an array of JSON objects of the routes available, for each route is provided: • line: line shot name
            • route: the route URI • routeName: optional route name • wktGeometry: the WKT geometry of the route • firstBusStop:
            name of the first bus stop • lastBusStop: name of the last bus stop</dd>
    </dl>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>